LivePages: Personalized Landing Pages for Email Click Targets

1. Concept Clarification

LivePages are not the same as the campaign composer. The campaign composer is the tool used to write the email sequence, while a LivePage is the dynamic, personalized web page that a recipient sees when they click a link in one of those emails.

• Campaign Composer: The tool for writing and scheduling emails.
• LivePage: The personalized landing page a recipient visits.

2. Functional Definition

Inputs

A LivePage is generated from the following inputs:

• Job Description (JD): The original job description that the user is applying for.
• User Variables: Data from the user's profile, such as their name, resume, and skills.
• Contact Variables: Data about the email recipient, such as their name, title, and company.

Outputs

The generated LivePage includes:

• A personalized greeting to the contact.
• A summary of the user's qualifications, tailored to the JD.
• A call to action (e.g., a link to the user's resume or a calendar to book a meeting).

Cache and URL Rules

• Caching: LivePages are cached for 24 hours to ensure fast loading times. The cache is automatically invalidated if the user updates their profile or the JD changes.
• URL Generation: Each LivePage is assigned a unique, unguessable URL (e.g., `https://live.roleferry.com/p/a1b2c3d4e5f6`). This ensures that only the intended recipient can view the page.

Privacy

LivePages are designed with privacy in mind. Access to a LivePage is restricted to the intended recipient via the unguessable URL. There is no public directory of LivePages.

3. End-to-End Example

Here is an example of how a LivePage is created and used in a campaign:

1. A user finds a job description (JD) for a "Software Engineer" role.
2. The user provides variables such as their resume, skills, and experience.
3. RoleFerry composes an outreach email to a hiring manager. The email includes a link to a personalized LivePage.
4. The LivePage is generated with a unique URL. It includes a personalized greeting to the hiring manager and highlights the user's skills that are most relevant to the JD.
5. The hiring manager clicks the link in the email and views the LivePage.
6. All interactions with the LivePage are tracked, providing the user with valuable insights into the hiring manager's engagement.

4. Assumptions and Dependencies

• Hosting Infrastructure: LivePages will require a robust hosting infrastructure that can handle a large number of dynamic pages with low latency.
• Analytics Service: An analytics service will be required to track user interactions with LivePages.
• Data Enrichment: The personalization of LivePages will depend on the availability and accuracy of data from our internal resume database and external enrichment services.